<!DOCTYPE html>
<html lang="en">
<head>
	<meta charset="UTF-8">
	<meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
	<title>fields | ElasticSearch 7.7 权威指南中文版</title>
	<meta name="keywords" content="ElasticSearch 权威指南中文版, elasticsearch 7, es7, 实时数据分析，实时数据检索" />
    <meta name="description" content="ElasticSearch 权威指南中文版, elasticsearch 7, es7, 实时数据分析，实时数据检索" />
    <!-- Give IE8 a fighting chance -->
    <!--[if lt IE 9]>
    <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
    <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
    <![endif]-->
	<link rel="stylesheet" type="text/css" href="../static/styles.css" />
	<script>
	var _link = 'multi-fields.html';
    </script>
</head>
<body>
<div class="main-container">
    <section id="content">
        <div class="content-wrapper">
            <section id="guide" lang="zh_cn">
                <div class="container">
                    <div class="row">
                        <div class="col-xs-12 col-sm-8 col-md-8 guide-section">
                            <div style="color:gray; word-break: break-all; font-size:12px;">原英文版地址: <a href="https://www.elastic.co/guide/en/elasticsearch/reference/7.7/multi-fields.html" rel="nofollow" target="_blank">https://www.elastic.co/guide/en/elasticsearch/reference/7.7/multi-fields.html</a>, 原文档版权归 www.elastic.co 所有<br/>本地英文版地址: <a href="../en/multi-fields.html" rel="nofollow" target="_blank">../en/multi-fields.html</a></div>
                        <!-- start body -->
                  <div class="page_header">
<strong>重要</strong>: 此版本不会发布额外的bug修复或文档更新。最新信息请参考 <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html" rel="nofollow">当前版本文档</a>。
</div>
<div id="content">
<div class="breadcrumbs">
<span class="breadcrumb-link"><a href="index.html">Elasticsearch Guide [7.7]</a></span>
»
<span class="breadcrumb-link"><a href="mapping.html">Mapping</a></span>
»
<span class="breadcrumb-link"><a href="mapping-params.html">Mapping parameters</a></span>
»
<span class="breadcrumb-node"><code class="literal">fields</code></span>
</div>
<div class="navheader">
<span class="prev">
<a href="mapping-field-meta.html">« <code class="literal">meta</code></a>
</span>
<span class="next">
<a href="normalizer.html"><code class="literal">normalizer</code> »</a>
</span>
</div>
<div class="section">
<div class="titlepage"><div><div>
<h2 class="title">
<a id="multi-fields"></a><code class="literal">fields</code><a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/mapping/params/multi-fields.asciidoc">edit</a>
</h2>
</div></div></div>
<p>It is often useful to index the same field in different ways for different
purposes.  This is the purpose of <em>multi-fields</em>. For instance, a <code class="literal">string</code>
field could be mapped as a <code class="literal">text</code> field for full-text
search, and as a <code class="literal">keyword</code> field for sorting or aggregations:</p>
<div class="pre_wrapper lang-console">
<pre class="programlisting prettyprint lang-console">PUT my_index
{
  "mappings": {
    "properties": {
      "city": {
        "type": "text",
        "fields": {
          "raw": { <a id="CO350-1"></a><i class="conum" data-value="1"></i>
            "type":  "keyword"
          }
        }
      }
    }
  }
}

PUT my_index/_doc/1
{
  "city": "New York"
}

PUT my_index/_doc/2
{
  "city": "York"
}

GET my_index/_search
{
  "query": {
    "match": {
      "city": "york" <a id="CO350-2"></a><i class="conum" data-value="2"></i>
    }
  },
  "sort": {
    "city.raw": "asc" <a id="CO350-3"></a><i class="conum" data-value="3"></i>
  },
  "aggs": {
    "Cities": {
      "terms": {
        "field": "city.raw" <a id="CO350-4"></a><i class="conum" data-value="3"></i>
      }
    }
  }
}</pre>
</div>
<div class="console_widget" data-snippet="snippets/768.console"></div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO350-1"><i class="conum" data-value="1"></i></a></p>
</td>
<td align="left" valign="top">
<p>The <code class="literal">city.raw</code> field is a <code class="literal">keyword</code> version of the <code class="literal">city</code> field.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO350-2"><i class="conum" data-value="2"></i></a></p>
</td>
<td align="left" valign="top">
<p>The <code class="literal">city</code> field can be used for full text search.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO350-3"><i class="conum" data-value="3"></i></a><a href="#CO350-4"></a></p>
</td>
<td align="left" valign="top">
<p>The <code class="literal">city.raw</code> field can be used for sorting and aggregations</p>
</td>
</tr>
</table>
</div>
<div class="note admon">
<div class="icon"></div>
<div class="admon_content">
<p>Multi-fields do not change the original <code class="literal">_source</code> field.</p>
</div>
</div>
<div class="tip admon">
<div class="icon"></div>
<div class="admon_content">
<p>New multi-fields can be added to existing
fields using the <a class="xref" href="indices-put-mapping.html" title="Put mapping API">PUT mapping API</a>.</p>
</div>
</div>
<div class="section">
<div class="titlepage"><div><div>
<h3 class="title">
<a id="_multi_fields_with_multiple_analyzers"></a>Multi-fields with multiple analyzers<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/mapping/params/multi-fields.asciidoc">edit</a>
</h3>
</div></div></div>
<p>Another use case of multi-fields is to analyze the same field in different
ways for better relevance. For instance we could index a field with the
<a class="xref" href="analysis-standard-analyzer.html" title="Standard Analyzer"><code class="literal">standard</code> analyzer</a> which breaks text up into
words, and again with the <a class="xref" href="analysis-lang-analyzer.html#english-analyzer" title="english analyzer"><code class="literal">english</code> analyzer</a>
which stems words into their root form:</p>
<div class="pre_wrapper lang-console">
<pre class="programlisting prettyprint lang-console">PUT my_index
{
  "mappings": {
    "properties": {
      "text": { <a id="CO351-1"></a><i class="conum" data-value="1"></i>
        "type": "text",
        "fields": {
          "english": { <a id="CO351-2"></a><i class="conum" data-value="2"></i>
            "type":     "text",
            "analyzer": "english"
          }
        }
      }
    }
  }
}

PUT my_index/_doc/1
{ "text": "quick brown fox" } <a id="CO351-3"></a><i class="conum" data-value="3"></i>

PUT my_index/_doc/2
{ "text": "quick brown foxes" } <a id="CO351-4"></a><i class="conum" data-value="3"></i>

GET my_index/_search
{
  "query": {
    "multi_match": {
      "query": "quick brown foxes",
      "fields": [ <a id="CO351-5"></a><i class="conum" data-value="4"></i>
        "text",
        "text.english"
      ],
      "type": "most_fields" <a id="CO351-6"></a><i class="conum" data-value="4"></i>
    }
  }
}</pre>
</div>
<div class="console_widget" data-snippet="snippets/769.console"></div>
<div class="calloutlist">
<table border="0" summary="Callout list">
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO351-1"><i class="conum" data-value="1"></i></a></p>
</td>
<td align="left" valign="top">
<p>The <code class="literal">text</code> field uses the <code class="literal">standard</code> analyzer.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO351-2"><i class="conum" data-value="2"></i></a></p>
</td>
<td align="left" valign="top">
<p>The <code class="literal">text.english</code> field uses the <code class="literal">english</code> analyzer.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO351-3"><i class="conum" data-value="3"></i></a><a href="#CO351-4"></a></p>
</td>
<td align="left" valign="top">
<p>Index two documents, one with <code class="literal">fox</code> and the other with <code class="literal">foxes</code>.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" width="5%">
<p><a href="#CO351-5"><i class="conum" data-value="4"></i></a><a href="#CO351-6"></a></p>
</td>
<td align="left" valign="top">
<p>Query both the <code class="literal">text</code> and <code class="literal">text.english</code> fields and combine the scores.</p>
</td>
</tr>
</table>
</div>
<p>The <code class="literal">text</code> field contains the term <code class="literal">fox</code> in the first document and <code class="literal">foxes</code> in
the second document.  The <code class="literal">text.english</code> field contains <code class="literal">fox</code> for both
documents, because <code class="literal">foxes</code> is stemmed to <code class="literal">fox</code>.</p>
<p>The query string is also analyzed by the <code class="literal">standard</code> analyzer for the <code class="literal">text</code>
field, and by the <code class="literal">english</code> analyzer for the <code class="literal">text.english</code> field.  The
stemmed field allows a query for <code class="literal">foxes</code> to also match the document containing
just <code class="literal">fox</code>.  This allows us to match as many documents as possible.  By also
querying the unstemmed <code class="literal">text</code> field, we improve the relevance score of the
document which matches <code class="literal">foxes</code> exactly.</p>
</div>

</div>
<div class="navfooter">
<span class="prev">
<a href="mapping-field-meta.html">« <code class="literal">meta</code></a>
</span>
<span class="next">
<a href="normalizer.html"><code class="literal">normalizer</code> »</a>
</span>
</div>
</div>

                  <!-- end body -->
                        </div>
                        <div class="col-xs-12 col-sm-4 col-md-4" id="right_col">
                        
                        </div>
                    </div>
                </div>
            </section>
        </div>
    </section>
</div>
<script src="../static/cn.js"></script>
</body>
</html>